System and method for an instant messaging interface

ABSTRACT

Computer-implemented systems and methods for a simplified instant messaging interface are provided for allowing users to initiate and engage in instant messaging conversations. In various embodiments, the systems and methods reduce the overhead involved in initiating and/or engaging in instant messaging conversations. In some embodiments, the simplified instant messaging interface allows users to initiate and or engage in conversations without having to open a separate standard messaging window for every conversation. In some embodiments, the simplified instant messaging interface may be used in conjunction with a standard instant messaging interface.

LIMITED COPYRIGHT AUTHORIZATION

A portion of the disclosure of this patent document includes materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightswhatsoever.

BACKGROUND OF THE DISCLOSURE

1. Field of the Disclosure

The present disclosure relates to the field of electronic systems forproviding instant messaging. More specifically, the present disclosurerelates to computer-implemented systems and methods for an instantmessaging interface.

2. Description of the Related Art

Instant messaging (“IM”) is a popular form of electronic communicationallowing users to communicate with each other in real-time. Instantmessaging is most commonly done over a computer network, and can beimplemented on mobile devices and other electronic devices. Each user isassociated with a unique user identification (“ID”). Most IM clientsoftware applications allow a user to create a messaging contact list(“buddy list”) which includes the ID's of the contacts that usercommonly communicates with using IM.

SUMMARY OF THE DISCLOSURE

Using a standard IM interface, an IM session may begin with a sendinguser initiating a conversation by selecting the ID of a recipient userthe sending user wishes to communicate with, causing a messaging windowassociated with the recipient user (“standard IM window”) to open. Thesending user then composes an instant message into the standard IMwindow and sends the message to the recipient user. The IM clientsoftware causes the message to be transmitted over a network to the IMclient software running on the recipient user's system. The recipientuser is notified of the message and may respond to it in a similarmanner. IM client software typically allows a user to simultaneouslyengage in multiple conversations with multiple users.

Using a standard IM interface, conversations often start with a sendinguser sending a message to find out if the recipient user is available toreceive a message. For example, sending users may send messages such as“yt?” (you there?), “ayt?” (are you there?), abbreviations which arecommonly used in IM. Using a standard IM interface, a standard IM windowremains open when the sending user waits to get the response. In manycases, a response may never be received and the conversation isabandoned. In such a case, both the sending and receiving users may haveto actively close the standard IM windows that were opened but werenever used for interaction. Thus one benefit of one embodiment of asimplified IM interface is that the overhead associated with usersinitiating conversations and/or having to actively open and closestandard IM windows in order to initiate conversations is reduced.

In addition, cluttering of a device screen with multiple applicationwindows can be burdensome. Computer users, for example, typically havemultiple windows open from various software applications, each windowtaking up limited space of a computer desktop. When too many windows areopen at the same time, it can become difficult to manage the desktopefficiently. A problem with current IM technology is that a separate,standard messaging window is opened for each conversation. Thus, oneimportant benefit of one embodiment of the simplified IM interfacedisclosed in the present application is that it allows users to engagein an IM conversation without having to open a separate standard IMmessaging window for each conversation.

One embodiment of the present disclosure is a computer-implementedmethod of providing a simplified instant messaging interface, wherein amessage-entry field is provided associated with a selected messagerecipient. The message-entry field may be integrated with a messagingcontact list. The method further includes receiving a message into themessage-entry field and sending the message to the selected messagerecipient.

Another embodiment is a system for providing a simplified instantmessaging interface, comprising an instant messaging client moduleconfigured to allow a user to communicate over a network with otherinstant messaging clients. The system further comprises a message-entrymodule in communication with the instant messaging client module,wherein the message-entry module comprises a message-entry fieldassociated with a selected message recipient which receives a messageand is integrated with a messaging contact list. The message-entrymodule sends the message to the selected message recipient.

A further embodiment is a computer-implemented method for executing acomputer application in a graphical user interface windowingenvironment. The method comprises displaying a message-entry fieldassociated with a selected message recipient and integrated with amessaging contact list within a graphical window. The method furthercomprises receiving a message into the message-entry field and sendingthe message to the selected message recipient.

Yet another embodiment is a computer-implemented method of providing asimplified instant messaging interface. The method comprises providing amessage-entry field associated with a messaging console, receiving amessage into the message-entry field and sending the message to aselected message recipient.

For purposes of summarizing the invention, certain aspects, advantagesand novel features have been described herein. Of course, it is to beunderstood that not necessarily all such aspects, advantages or featureswill be embodied in any particular embodiment. Moreover, it is to beunderstood that not necessarily all such advantages or benefits may beachieved in accordance with any particular embodiment of the invention.Thus, for example, those skilled in the art will recognize that theinvention may be embodied or carried out in a manner that achieves oneadvantage or group of advantages as taught herein without necessarilyachieving other advantages or benefits as may be taught or suggestedherein.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other features will now be described with reference to thedrawings summarized below. These drawings and the associated descriptionare provided to illustrate a preferred embodiment of the invention, andnot to limit the scope of the invention.

FIG. 1 illustrates a high-level diagram of one embodiment of a networktopology over which IM users communicate.

FIG. 2 illustrates an example of a screen display of a standard IM chatsession.

FIGS. 3A-E sequentially illustrate one embodiment of an IM conversationusing one embodiment of a simplified IM interface.

FIG. 4 illustrates a high-level diagram of one embodiment of a computingsystem in which an IM client may be implemented.

FIG. 5 is one embodiment of a high-level flow chart illustrating oneembodiment of a simplified IM interface, viewed from the perspective ofthe IM client software.

FIG. 6 is one embodiment of a high-level flow chart illustrating oneembodiment of a simplified IM interface, viewed from the perspective ofthe user.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Systems and methods which represent various embodiments and exampleapplications of the present disclosure will now be described withreference to the drawings. For purposes of illustration, someembodiments will be described in the context of IM systems and methodsimplemented on a computer. However, the present invention is not limitedby the type of environment in which the systems and methods are used;the systems and methods may be used in other environments, such as, forexample, cell phones, other mobile devices and so forth. Moreover, thespecific implementations described herein are set forth in order toillustrate, and not to limit, the invention.

I. Overview

For purposes of providing an overview of some embodiments, certainaspects, advantages, benefits, and novel features of the invention aredescribed herein. It is to be understood that not necessarily all suchadvantages or benefits may be achieved in accordance with any particularembodiment of the invention. Thus, for example, those skilled in the artwill recognize that the invention may be embodied or carried out in amanner that achieves one advantage or group of advantages as taughtherein without necessarily achieving other advantages or benefits as maybe taught or suggested herein.

In accordance with the present disclosure, a simplified IM interface isprovided. In one embodiment, for example, users are able to initiate,respond to, and generally exchange instant messages using the simplifiedIM interface. One benefit of one embodiment of the simplified IMinterface is that it allows users to initiate and engage in IMconversations without opening a standard IM messaging window.

In one embodiment, the simplified IM interface can be used in a systemsimilar to the one illustrated in FIG. 1, which illustrates a high-leveldiagram of one embodiment of a network topology over which IM userscommunicate. In one embodiment, an IM client system 100 communicates viaa network 140 to another IM client system 110. The IM client systems100, 110 communicates with an IM server system 120 which communicateswith an IM database 130. There may be any number of IM client 100, 110and server 120 systems. In the illustrated embodiment, the IM client100, 110 and server 120 systems are computer systems. In otherembodiments, the IM client 100, 110 and server 120 systems may be othertypes of devices, such as, for example, mobile devices. In someembodiments, the IM client 100, 110 and server 120 systems may be anycombination of different types of devices. For example, in oneembodiment, some of the client systems 100, 110 may be computer systems,some may be mobile devices, and the server system 120 system may be acomputer system.

In some embodiments, IM server system 120 maintains the IM database 130which includes the IM users authorized to communicate over the IMnetwork. The IM server system 120 may include other information,including, for example, personal user information, buddy lists, e-mailaddresses of users. In some embodiments, the IM server system 120receives messages from IM client systems 100, 110 addressed to a desiredmessage recipient, and sends the messages to the IM client systems 100,110. The illustrated example is just one embodiment of a topology inwhich an IM system may be implemented. In some embodiments, for example,the IM server system 120 and IM database 130 may not be included in thenetwork topology and IM client systems 100, 110 communicate directlywithout the intervention of the IM server system 120.

II. Embodiment of a Standard IM Chat Session

FIG. 2 illustrates one embodiment of a screen display of a user who isusing a standard IM interface. In the illustrated embodiment, the screendisplay 200, a computer desktop in this embodiment, includes a standardIM interface which includes a plurality of standard IM messaging windows220, 230, 240, 250, 260 and a messaging console 210. In someembodiments, the messaging console 210 includes a login function (notshown) which allows the user to log-in to the user's account. Themessaging console may also include a number of possible features whichare well known to those of skill in the art and are not necessarilyshown in the illustrated embodiment. For example, the console may allowa user to change his or her on-line status (for example, from “on-line”to “away”) to indicate to other users whether or not that user isavailable to receive messages.

In the illustrated embodiment, the messaging console 210 includes amessaging contact, or “buddy” list 211, which may include a number oficons or regions 212 corresponding to the contacts that user mayfrequently communicate with. In some embodiments, the user may select amessaging contact with which they wish to communicate (for example,“Steve”) by selecting the associated icon or region such as, forexample, by clicking or double-clicking. The IM interface will then, insome embodiments, open a messaging window 220 associated with thatcontact. In some embodiments, the messaging window 220 includes aconversation transcript display area 222 which displays a transcript ofthe conversation between the user and the contact. In some embodiments,the messaging window further includes a message entry field 223 intowhich the sending user can type a message. The user then indicates theywant to send the message. For example, in some embodiments, the user maytype “Enter” on the keyboard, or may click on a “Send” button (notshown) associated with the message entry field 223 to send the message.As illustrated, in some embodiments, a user who engages in multipleconversations simultaneously in a standard IM interface have manystandard IM windows 220, 230, 240, 250, 260 open at any given time.

III. Embodiment of a Sample IM Conversation Using a Simplified IMInterface

FIGS. 3A-E sequentially illustrate one embodiment of an IM conversationusing one embodiment of a simplified IM interface. FIG. 3A illustrates amessaging console 300 for a user, Steve, who has two contacts, Nancy andPaul, in his messaging contact list 310. At some point, Steve decides tosend a message to Nancy using the simplified IM interface to determinewhether or not Nancy is available to have an IM conversation. Asillustrated by FIG. 3B, Steve activates the simplified IM interface byopening a simplified message entry field 320 which is associated withand/or integrated with the messaging contact list 310 and does not, inthis embodiment, open a standard messaging window. In variousembodiments, for example, Steve may activate the simplified messageentry field 320 by hovering over, clicking-on or highlighting the region330 associated with Nancy or a portion thereof 331, 332, 333 in themessaging contact list 310. As illustrated, Steve types “ayt?”, shortfor “Are you there?” into the simplified message entry field 320 andsends the message to Nancy, for example, in some embodiments, bypressing the “Enter” key on the keyboard. Those of skill in the art willappreciate that region 330 may be configured in any number of ways inorder to allow for the activation of the simplified IM interface. Forexample, in some embodiments, there may be only one portion 331, 332,333 that allows for the activation of the simplified IM interface.Alternatively, in other embodiments, there may be more or differenttypes of portions 331, 332, 333 that allow for activation of thesimplified IM interface.

As illustrated in FIG. 3C, in this embodiment, Nancy replies to Steve'smessage. Her response, “yes I'm here” is indicated in the responsenotification window 340. Steve then decides to continue the conversationusing the simplified IM interface in a manner similar to that describedin FIG. 3B. This time Steve types “cool how r u”, shorthand for “cool,how are you?,” into the simplified message entry field 320 and sends themessage.

As depicted by FIG. 3D, at a later point in the conversation, Stevebegins to send another note to Nancy, “how is work goi,” into thesimplified message entry field 320 using the simplified IM interface. Asillustrated by FIG. 3E, in this embodiment, a standard messaging window350 opens once a threshold message size is reached in the simplifiedmessage entry field 320. In the illustrated embodiment, the thresholdmessage size is 16. Once Steve types character number 16 (includingspaces) into the message entry field 320, a standard messaging window350 opens, displaying a transcript of their conversation to that pointin transcript display area 351. Steve's current message is alsodisplayed in standard message entry field 352.

FIGS. 3A-E illustrate one example of a conversation using the simplifiedIM interface. Many variations of the conversation are possible utilizingthe simplified IM interface. For example, in another conversation, thesending user may send two messages using the simplified IM interfacebefore receiving a response from the desired message recipient, or maynever in fact receive a response. Moreover, the simplified IM interfacecan, in some embodiments, be used in combination with the standard IMinterface. For example, the user may decide to send the initial messageusing the simplified IM interface and respond to the reply from themessage recipient using the standard IM interface. Alternatively, forexample, the user could decide to hold the entire conversation in thesimplified IM interface, or entirely in the standard IM interface. Theuser may go back and forth between using the simplified IM interface andthe standard IM interface during the same conversation. In otherembodiments, the simplified IM interface may be activated for certaincontacts in the user's contact list but not others. For example, Stevemay choose to activate the simplified IM interface for Nancy, but notfor Paul, or vice versa.

Moreover, in other embodiments, the simplified message entry field 320may be activated by other mechanisms, including, for example, by voiceactivation, or by typing a key or a combination of keys. In someembodiments, the simplified message entry field 320 may appear anddisappear in different ways. For example, in the illustrated embodiment,the message entry field 320 appears after activated (for example, by aclick) and disappears once the message is sent. In other embodiments,the simplified message entry field 320 may remain after the message issent and may appear in the messaging contact list 310 without separateactivation.

Further, in other embodiments the simplified message entry field 320 mayappear in different locations. For example, in some embodiments, thesimplified message entry field 320 may be located within the messagingcontact list 310. In other embodiments, the message entry field 320 maybe located within the messaging console 300 but not within the messagingcontact list 310. In various embodiments, portions of the simplifiedmessage entry field 320 may overlap with portions of the messagingcontact list 310 and/or messaging console 300. In further embodiments,the simplified message entry field 320 may be integrated with theresponse notification window 340 in addition to or instead of with themessaging contact list 310. The simplified message entry field 320 mayappear in different locations on the desktop. For example, in someembodiments, the simplified message entry field 320 may appear adjacentto, rather than on or within, the messaging console 300.

In other embodiments, the message entry field 320 may include variousadditional features. For example, the message entry field 320 mayinclude icons associated with the recipient contact, or any other typeof icon. For example, the message entry field may include the user'son-line status indicator or name. In other embodiments, the messageentry field 320 may include a conversation transcript or a partialconversation transcript.

In yet other embodiments, the simplified IM interface may be limited tosimplifying conversation initiation. For example, in some embodiments,once the first initiating message (for example, “ayt?”) using thesimplified IM interface is answered, a standard IM window 350 may openedfor both the sending and responding users.

For the sake of simplicity, FIG. 3 illustrates one example of aconversation using the simplified IM interface from the perspective ofthe sending IM client. However, the simplified IM interface may be usedby the responding (message recipient) IM client as well in a similarfashion.

IV. Embodiment of a Simplified IM Implemented in a Computing System

FIG. 4 illustrates a high-level diagram of one embodiment of a computingsystem 400 in which an IM client system 400 may be implemented. Thecomputing system 400 includes, for example, a personal computer that isIBM, Macintosh, or Linux/Unix compatible. In one embodiment, thecomputing system 400 comprises a server, personal computer (PC), alaptop computer, a cell phone, a personal digital assistant, a kiosk,Blackberry® device, or an audio player, for example. In otherembodiments, the computing system 400 system is another type of portablecomputing device, a computer workstation, a local area network ofindividual computers, an interactive wireless communications device, ahandheld computer, an embedded computing device, or the like. In oneembodiment, the exemplary computing system 400 includes a centralprocessing unit (“CPU”) 405, which may include a conventionalmicroprocessor. The computing system 400 further includes a memory 430,such as random access memory (“RAM”) for temporary storage ofinformation and a read only memory (“ROM”) for permanent storage ofinformation, and a mass storage device 420, such as a hard drive,diskette, or optical media storage device. Typically, the modules of thecomputing system 400 are connected to the computer using a standardsbased bus system. In different embodiments, the standards based bussystem could be Peripheral Component Interconnect (“PCI”), Microchannel,SCSI, Industrial Standard Architecture (“ISA”) and Extended ISA (“EISA”)architectures, for example.

The computing system 400 is generally controlled and coordinated byoperating system software, such as Windows 95, Windows 98, Windows NT,Windows 2000, Windows XP, Windows Vista, Linux, SunOS, Solaris, or othercompatible operating systems. In Macintosh systems, the operating systemmay be any available operating system, such as MAC OS X. In otherembodiments, the computing system 400 may be controlled by a proprietaryoperating system. Conventional operating systems control and schedulecomputer processes for execution, perform memory management, providefile system, networking, I/O services, and provide a user interface,such as a graphical user interface (“GUI”), among other things.

The exemplary computing system 400 includes one or more commonlyavailable input/output (I/O) devices and interfaces 410, such as akeyboard, mouse, touchpad, and printer. In one embodiment, the I/Odevices and interfaces 410 include one or more display device, such as amonitor, that allows the visual presentation of data to a user. Moreparticularly, a display device provides for the presentation of GUIs,application software data, and multimedia presentations, for example.The computing system 400 may also include one or more multimedia devices440, such as speakers, video cards, graphics accelerators, andmicrophones, for example.

In the embodiment of FIG. 4, the I/O devices and interfaces 410 providea communication interface to various external devices. In one embodimentof FIG. 4, the computing system 400 is electronically coupled to anetwork. The network 140 communicates with various computing devicesand/or other electronic devices via wired or wireless communicationlinks.

In the embodiment of FIG. 4, the computing system 400 also includes anIM client module 450 and a simplified message-entry module 460 that maybe executed by the CPU 405. The IM client module 450 is configured toallow a user to communicate over network 140 with other IM clients. Thesimplified message-entry module 460 is in communication with the IMclient module. These modules implement the processes and featuresdescribed in greater detail above with respect to FIG. 3, and describedbelow with FIGS. 5 and 6. These modules may include, by way of example,components, such as software components, object-oriented softwarecomponents, class components and task components, processes, functions,attributes, procedures, subroutines, segments of program code, drivers,firmware, microcode, circuitry, data, databases, data structures,tables, arrays, and variables. In other embodiments, IM client module450 and the simplified message entry module 460 may be implemented asone module.

V. Embodiments of the Method of Operation of a Simplified IM Interface

FIG. 5 is a high-level flow chart illustrating one embodiment of thesimplified IM interface, viewed from the perspective of the IM clientsoftware of the sender. In one embodiment, the IM client detects atstate 510 when a user selects a desired message recipient from themessaging contact list by, for example, hovering the cursor over,clicking on or high-lighting the identifier associated with the contactin the contact list. The IM client then activates a simplifiedmessage-entry field at state 520 which, in some embodiments, isintegrated with the messaging contact list as described above withrespect to FIG. 3. The IM client then receives a message into thesimplified message-entry field from the user at state 530.

As indicated by decision state 5 40, in some embodiments, a standardmessaging window interface will open if the user types a message withmore characters than a threshold message size associated with thesimplified message-entry field. In some embodiments, the thresholdmessage size is significantly less than the amount displayed in astandard messaging window. For example, the threshold message size mayin other embodiments be less than 20 characters, between 20 charactersand 100 characters, or greater than 100 characters. In some embodiments,the threshold message size is based on the language of communication.For example the threshold message size may be different in German thanin Russian. In some embodiments, the threshold message size may bedecided based on an evaluation of usage. For example, if a particularclass or category of users is, based on an evaluation of IM usage bythat class or category, determined to generally initiate conversationsusing 30 characters or less, the threshold size for that class orcategory of users may be set to 30 characters. In some embodiments, thethreshold message size is based on the user's display, font size,display size and so forth. In various embodiments, the threshold messagesize can be 16, 20 or 100 characters. These particular embodiments arepresented by way of example only.

If the threshold message size is not reached, the IM client will thendetect when or receive an indication that the user has decided to sendthe message at state 560, and will subsequently transmit the message tothe message recipient. For example, the user may press the “Enter” keyto indicate that the user wants to send the message. Typically, theconversation will continue by the IM client receiving a response fromthe message recipient at state 570 and indicating that the response wasreceived by, for example, opening a response notification window whichmay be a standard IM window or simplified IM field at state 580. Theoriginal sender may then want to reply to the response using thesimplified IM interface. The IM client will detect user selection of themessage recipient at state 590 in a manner similar to that of state 510.When replying to the response, the simplified message entry field may beintegrated with the messaging contact list or, alternatively, in someembodiments, with the response notification window.

FIG. 6 is a high-level flow chart illustrating one embodiment of asimplified IM interface, but viewed from the perspective of the sendinguser. The user will selects a desired message recipient from themessaging contact list at state 610 by, for example, hovering the cursorover, clicking on, or high-lighting the identifier associated with thecontact in the contact list. The user will then type a message into thesimplified message-entry field at state 620.

As indicated by decision state 630 and described above with respect toFIG. 5, in some embodiments, a standard messaging window interface willopen at state 640 if the user types a message with more characters thana threshold message size associated with the simplified message-entryfield. If the threshold message size is not reached, the user may thendecide to send the message at state 650 by, for example, pressing the“Enter” key to indicate that they want to send the message. Typically,the conversation will continue by user waiting for and then receiving aresponse from the message recipient at state 660. The user may then wantto reply to the response using the simplified IM interface by selectingthe message recipient at state 670 in a manner similar to that of state610. When replying to the recipient's response at state 670, thesimplified message entry field may be integrated with the messagingcontact list or, alternatively, in some embodiments, in other parts ofthe IM interface. For example, the message entry field may be integratedwith the response notification window.

For simplicity, FIGS. 5 and 6 illustrate the general flow of aconversation by means of certain embodiments using the simplified IMinterface. The steps may be ordered differently depending on theconversation. For example, in other conversations, the sending user maysend two messages using the simplified IM interface before receiving aresponse from the desired message recipient, or may never in factreceive a response. Moreover, the simplified IM interface can, in someembodiments, be used in combination with the standard IM interface. Forexample, the user may decide to send the initial message using thesimplified IM interface and respond to the reply from the messagerecipient using the standard IM interface or vice versa. Alternatively,for example, the user could decide to hold the entire conversation inthe simplified IM interface. For the sake of simplicity, FIGS. 5 and 6illustrate embodiments of conversations using the simplified IMinterface from the perspective of the sending IM client and sendinguser. However, the simplified IM interface may be used by the respondingIM client and responding user as well.

VI. Additional Embodiments

Although systems and methods are disclosed with reference to preferredembodiments, the invention is not intended to be limited thereby.Rather, a skilled artisan will recognize from the disclosure herein awide number of alternatives for providing a simplified IM interface.

In general, the word “module,” as used herein, refers to logic embodiedin hardware or firmware, or to a collection of software instructions,possibly having entry and exit points, written in a programminglanguage, such as, for example, Java, Lua, C or C++. A software modulemay be compiled and linked into an executable program, installed in adynamic link library, or may be written in an interpreted programminglanguage such as, for example, BASIC, Perl, or Python. It will beappreciated that software modules may be callable from other modules orfrom themselves, and/or may be invoked in response to detected events orinterrupts. Software instructions may be embedded in firmware, such asan EPROM. It will be further appreciated that hardware modules may becomprised of connected logic units, such as gates and flip-flops, and/ormay be comprised of programmable units, such as programmable gate arraysor processors. The modules described herein are preferably implementedas software modules, but may be represented in hardware or firmware.Generally, the modules described herein refer to logical modules thatmay be combined with other modules or divided into sub-modules despitetheir physical organization or storage.

The network 140 may include one or more of any type of electronicallyconnected group of devices including, for instance, the followingnetworks: a virtual private network, a public Internet, a privateInternet, a secure Internet, a private network, a public network, avalue-added network, a local area network (LAN), a wide area network(WAN), a wired network, a wireless network, an intranet, an extranet,the Internet, a telephone network, a cable television network, voiceover IP (VOIP), data, voice and video over IP (DVVOIP), and/or any othertype of network or combination of networks. In one embodiment, thenetwork 140 may be capable of providing video, audio, and/or datacommunications. In addition, the connectivity to the network 140 may be,for example, remote modem, Ethernet (IEEE 802.3), Token Ring (IEEE802.5), Fiber Distributed Datalink Interface (FDDI) or AsynchronousTransfer Mode (ATM).

In various embodiments, the computing system 200 may include aconventional general purpose single-chip or multi-chip microprocessorsuch as a Pentium® processor, a Pentium® II processor, a Pentium® Proprocessor, an xx86 processor, an 8051 processor, a MIPS™ processor, aPower PC® processor, or an ALPHA® processor. In addition, themicroprocessor may be any conventional special purpose microprocessorsuch as a digital signal processor. Furthermore, the computing system200 may be used in connection with various operating systems such as:Microsoft® Windows® 3.X, Microsoft® Windows 95, Microsoft® Windows 98,Microsoft® Windows® NT, Microsoft® XP, Microsoft® Vista, Microsoft®Windows® CE, Palm Pilot OS, OS/2, Apple® MacOS®, Disk Operating System(DOS), UNIX, Linux®, VxWorks, or IBM® OS/2®, Sun OS, Solaris OS, IRIX OSoperating systems, and so forth.

It is also recognized that the term “remote” may include data, objects,devices, components, and/or modules not stored locally, that is notaccessible via the local bus. Thus, remote data may include a devicewhich is physically stored in the same room and connected to the user'sdevice via a network. In other situations, a remote device may also belocated in a separate geographic area, such as, for example, in adifferent location, country, and so forth.

Although the foregoing invention has been described in terms of certainpreferred embodiments, other embodiments will be apparent to those ofordinary skill in the art from the disclosure herein. Moreover, thedescribed embodiments have been presented by way of example only, andare not intended to limit the scope of the inventions. Indeed, the novelmethods and systems described herein may be embodied in a variety ofother forms without departing from the spirit thereof. Accordingly,other combinations, omissions, substitutions and modifications will beapparent to the skilled artisan in view of the disclosure herein.

1. A computer-implemented method of providing a simplified instantmessaging interface, comprising: providing a message-entry fieldassociated with a selected message recipient and integrated with amessaging contact list; receiving a message into the message-entryfield; and sending the message to the selected message recipient.
 2. Themethod of claim 1, wherein the message-entry field is integrated with aresponse notification window.
 3. The method of claim 1, wherein themessage-entry field is integrated with a messaging contact list or aresponse notification window.
 4. The method of claim 1, furthercomprising initiating a standard messaging window after a thresholdmessage size is received into the message-entry field.
 5. The method ofclaim 4, wherein the threshold message size is significantly less thanthe amount displayed in a standard messaging window.
 6. The method ofclaim 4, wherein the threshold message size is 20 characters.
 7. Themethod of claim 4, wherein the threshold message size is 100 characters.8. The method of claim 4, wherein the threshold message size is based onthe language of communication.
 9. The method of claim 1, furthercomprising automatically opening the message-entry field after aresponse is received from a message recipient.
 10. A storage mediumhaving a computer program stored thereon for causing a suitableprogrammed system to process computer-program code by performing thecomputer implemented method of claim 1 when such program is executed onthe system.
 11. A computer system programmed to perform the method ofclaim
 1. 12. A system for providing a simplified instant messaginginterface, comprising: an instant messaging client module configured toallow a user to communicate over a network with other instant messagingclients; and a message-entry module in communication with the instantmessaging client module, wherein the message-entry module comprises amessage-entry field associated with a selected message recipient whichreceives a message and is integrated with a messaging contact list,wherein the message-entry module sends the message to the selectedmessage recipient.
 13. The system of claim 12, wherein the message-entryfield is integrated with a response notification window.
 14. The systemof claim 12, wherein the message-entry field is integrated with amessaging contact list or a response notification window.
 15. The systemof claim 12, wherein the message-entry module is further configured toinitiate a standard messaging window after a threshold message size isreceived into the message-entry field.
 16. The system of claim 15,wherein the threshold message size is significantly less than the amountof message displayed in a standard messaging window.
 17. The method ofclaim 15, wherein the threshold message size is 20 characters.
 18. Thesystem of claim 15, wherein the threshold message size is 100characters.
 19. The system of claim 15, wherein the threshold messagesize is based on the language of communication.
 20. The system of claim12, wherein the message-entry module is further configured toautomatically open the message-entry field after a response is receivedfrom a message recipient.
 21. A computer-readable medium having storedthereon a computer program which embodies the system of claim
 12. 22. Acomputer-implemented method for executing a computer application in agraphical user interface windowing environment, comprising: displaying amessage-entry field associated with a selected message recipient andintegrated with a messaging contact list within a graphical window;receiving a message into the message-entry field; and sending themessage to the selected message recipient.
 23. A computer-implementedmethod of providing a simplified instant messaging interface,comprising: providing a message-entry field associated with a messagingconsole; receiving a message into the message-entry field; and sendingthe message to a selected message recipient.